| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CP.4.6.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.4.6 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CP_4_6_Manage_Orders_for_Referral |
| Title | CP.4.6 Manage Orders for Referral (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Enable the origination, documentation and tracking of referrals between care providers or healthcare organizations, including clinical and administrative details of the referral, and consents and authorizations for disclosures as required. |
| Purpose | Documentation and tracking of a referral from one care provider to another is supported, whether the referred to or referring providers are internal or external to the healthcare organization. Guidelines for whether a particular referral for a particular patient is appropriate in a clinical context and with regard to administrative factors such as insurance may be provided to the care provider at the time the referral is created. The EHR-S provides the ability to receive and act upon referral responses from providers. The EHR-S may provide the ability to capture completion of the referral appointment. Referrals may be received electronically (i.e. e-Referrals); or may be received non-electronically. If non-electronic, the system needs to allow the user to capture the referral information and manage referral request. If the system supports e-Referrals, then the system will also need to support additional functionality to manage the receipt of the referral request. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Enable the origination, documentation and tracking of referrals between care providers or healthcare organizations, including clinical and administrative details of the referral, and consents and authorizations for disclosures as required.
Documentation and tracking of a referral from one care provider to another is supported, whether the referred to or referring providers are internal or external to the healthcare organization. Guidelines for whether a particular referral for a particular patient is appropriate in a clinical context and with regard to administrative factors such as insurance may be provided to the care provider at the time the referral is created. The EHR-S provides the ability to receive and act upon referral responses from providers. The EHR-S may provide the ability to capture completion of the referral appointment. Referrals may be received electronically (i.e. e-Referrals); or may be received non-electronically. If non-electronic, the system needs to allow the user to capture the referral information and manage referral request. If the system supports e-Referrals, then the system will also need to support additional functionality to manage the receipt of the referral request.
| CP.4.6#01 | SHALL |
The system SHALL provide the ability to manage outbound referral(s), whether internal or external to the organization. |
| CP.4.6#02 | dependent SHALL |
The system SHALL provide the ability to capture clinical details necessary for the referral according to scope of practice of the referral recipient. |
| CP.4.6#03 | dependent SHALL |
The system SHALL provide the ability to link (e.g., link to image stored in PACS) clinical details as necessary for the referral according to scope of practice of the referral recipient. |
| CP.4.6#04 | dependent SHALL |
The system SHALL provide the ability to render clinical details as appropriate for the referral according to scope of practice of the referral recipient (e.g., clinical details required for dermatologist differ from those required by oncologist). |
| CP.4.6#05 | SHOULD |
The system SHOULD provide the ability to capture administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral. |
| CP.4.6#06 | SHOULD |
The system SHOULD provide the ability to link to administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral. |
| CP.4.6#07 | SHOULD |
The system SHOULD provide the ability to render administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral. |
| CP.4.6#08 | SHALL |
The system SHALL provide the ability to capture, store, and render an inbound referral response (e.g., referral accepted, referral denied, or more information needed). |
| CP.4.6#09 | SHALL |
The system SHALL provide the ability to determine and render recommended actions based on an inbound referral response (e.g., referral accepted, referral denied, or more information needed). |
| CP.4.6#10 | MAY |
The system MAY provide the ability to capture a notification that the patient fulfilled a referred appointment. |
| CP.4.6#11 | SHOULD |
The system SHOULD provide the ability to determine and render diagnosis-based clinical guidelines for making a referral. |
| CP.4.6#12 | SHOULD |
The system SHOULD provide the ability to determine the contents of a referral order by rendering order sets for review by the provider. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CP.4.6",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Enable the origination, documentation and tracking of referrals between care providers or healthcare organizations, including clinical and administrative details of the referral, and consents and authorizations for disclosures as required.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Documentation and tracking of a referral from one care provider to another is supported, whether the referred to or referring providers are internal or external to the healthcare organization. Guidelines for whether a particular referral for a particular patient is appropriate in a clinical context and with regard to administrative factors such as insurance may be provided to the care provider at the time the referral is created. The EHR-S provides the ability to receive and act upon referral responses from providers. The EHR-S may provide the ability to capture completion of the referral appointment. Referrals may be received electronically (i.e. e-Referrals); or may be received non-electronically. If non-electronic, the system needs to allow the user to capture the referral information and manage referral request. If the system supports e-Referrals, then the system will also need to support additional functionality to manage the receipt of the referral request.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage outbound referral(s), whether internal or external to the organization.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture clinical details necessary for the referral according to scope of practice of the referral recipient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to link (e.g., link to image stored in PACS) clinical details as necessary for the referral according to scope of practice of the referral recipient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render clinical details as appropriate for the referral according to scope of practice of the referral recipient (e.g., clinical details required for dermatologist differ from those required by oncologist).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to link to administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture, store, and render an inbound referral response (e.g., referral accepted, referral denied, or more information needed).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to determine and render recommended actions based on an inbound referral response (e.g., referral accepted, referral denied, or more information needed).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture a notification that the patient fulfilled a referred appointment.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine and render diagnosis-based clinical guidelines for making a referral.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.6#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine the contents of a referral order by rendering order sets for review by the provider.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.4.6",
"version" : "2.1.0",
"name" : "CP_4_6_Manage_Orders_for_Referral",
"title" : "CP.4.6 Manage Orders for Referral (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Enable the origination, documentation and tracking of referrals between care providers or healthcare organizations, including clinical and administrative details of the referral, and consents and authorizations for disclosures as required.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Documentation and tracking of a referral from one care provider to another is supported, whether the referred to or referring providers are internal or external to the healthcare organization. Guidelines for whether a particular referral for a particular patient is appropriate in a clinical context and with regard to administrative factors such as insurance may be provided to the care provider at the time the referral is created. The EHR-S provides the ability to receive and act upon referral responses from providers. The EHR-S may provide the ability to capture completion of the referral appointment. Referrals may be received electronically (i.e. e-Referrals); or may be received non-electronically. If non-electronic, the system needs to allow the user to capture the referral information and manage referral request. If the system supports e-Referrals, then the system will also need to support additional functionality to manage the receipt of the referral request.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-01",
"label" : "CP.4.6#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage outbound referral(s), whether internal or external to the organization.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.4.6-02",
"label" : "CP.4.6#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture clinical details necessary for the referral according to scope of practice of the referral recipient.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.4.6-03",
"label" : "CP.4.6#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to link (e.g., link to image stored in PACS) clinical details as necessary for the referral according to scope of practice of the referral recipient.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CP.4.6-04",
"label" : "CP.4.6#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render clinical details as appropriate for the referral according to scope of practice of the referral recipient (e.g., clinical details required for dermatologist differ from those required by oncologist).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-05",
"label" : "CP.4.6#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-06",
"label" : "CP.4.6#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to link to administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-07",
"label" : "CP.4.6#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render administrative details (e.g., insurance information, consents and authorizations for disclosure) as necessary for the referral.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-08",
"label" : "CP.4.6#08",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture, store, and render an inbound referral response (e.g., referral accepted, referral denied, or more information needed)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-09",
"label" : "CP.4.6#09",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to determine and render recommended actions based on an inbound referral response (e.g., referral accepted, referral denied, or more information needed)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-10",
"label" : "CP.4.6#10",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture a notification that the patient fulfilled a referred appointment.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-11",
"label" : "CP.4.6#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine and render diagnosis-based clinical guidelines for making a referral.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.6-12",
"label" : "CP.4.6#12",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine the contents of a referral order by rendering order sets for review by the provider.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.2.4#7"
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.